Release 10.1A: OpenEdge Development:
Programming Interfaces

Managing auditing IDs

By default, OpenEdge uses the database connection ID as the auditing ID. As described in earlier sections, OpenEdge can otherwise take the auditing ID for a given database from the Progress session ID, depending on a setting in database auditing options. No matter what source you use for the auditing ID, you might note the following points:

The auditing ID only specifies the value recorded as the user ID in audit event records and has no effect on database authorization, either for table and field access or for auditing privileges. The effective database connection ID for each database always controls database access and auditing privileges.
If you configure the database option to trust the application domain registry, this causes both the 4GL SET-DB-CLIENT function and the SET-CLIENT( ) method on the SECURITY-POLICY system handle to assert and validate the database connection ID using the application’s trusted domain registry (instead of using the database’s own trusted domain registry). If you use SET-CLIENT( ) with this database option to set the database connection ID, which also asserts and validates the Progress session ID, the effective auditing ID is identical to the Progress session ID, regardless of any setting database auditing options that you set.

For more information on managing the auditing ID within a Progress session, see Chapter 3, " Auditing."